Skip to content

fix: remove continuation behavior from reference integrations - #63

Merged
rlippmann merged 4 commits into
mainfrom
remove_continuation
Aug 9, 2026
Merged

fix: remove continuation behavior from reference integrations#63
rlippmann merged 4 commits into
mainfrom
remove_continuation

Conversation

@rlippmann

Copy link
Copy Markdown
Owner

Summary

Removes continuation behavior from the reference integrations.

This changes failed transitions from a resumable interaction model into a rejected current-request model:

  • failed transitions do not create resumable state;
  • later user input is treated as a new request;
  • successful authoritative state transitions continue to persist normally.

Also simplifies the reference integration layer by removing stale continuation-era code and sharing duplicated LiteLLM adapter plumbing.

Why

The previous integration examples included continuation/clarification behavior where failed transitions could leave state that was completed by a later user response.

That model is no longer part of Context Compiler.

The reference integrations should demonstrate the current enforcement boundary:

user request → compiler decision → apply or reject → preserve authoritative state

This cleanup establishes a simpler baseline before adding DirectiveDrafter + HITL flows.

Example metadata

  • Enforcement point: LiteLLM proxy hook and OpenWebUI pipe integration boundaries
  • Domain: General context/state enforcement
  • Technology/runtime: LiteLLM Proxy, OpenWebUI Pipe, Python
  • Example type: reference integration
  • Does this use directive drafter? should normally be no: No (existing drafter variants were updated only to remove old continuation behavior; no new drafter flow added)
  • Does this derive state from model output? must be no for primary examples: No

Checklist

  • Repository scaffolding / governance change
  • One primary enforcement point
  • Explicit authoritative state
  • No model-derived state mutation
  • Adversarial stub or equivalent test
  • Observable runtime behavior change
  • Domain vocabulary is natural
  • Framework is secondary to the enforcement point
  • Docs updated
  • Tests/smoke checks added where practical

Notes

LiteLLM changes:

  • Failed transitions no longer overwrite saved checkpoints.
  • Existing persistent/stateless session handling is preserved.
  • Shared LiteLLM support helpers were extracted for duplicated request/state rendering plumbing.

OpenWebUI changes:

  • Failed transitions restore the prior in-memory engine state.
  • Clarification/resume terminology and behavior were removed.
  • Unused continuation-era helper code was removed.

This PR intentionally does not add DirectiveDrafter approval flows or HITL behavior. It only establishes the post-continuation integration baseline.

@rlippmann
rlippmann merged commit 5018785 into main Aug 9, 2026
6 checks passed
@rlippmann
rlippmann deleted the remove_continuation branch August 9, 2026 04:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant